🚨 [security] Update all of nextjs 16.1.0 → 16.1.6 (patch) by depfu[bot] · Pull Request #19609 · tailwindlabs/tailwindcss

depfu · 2026-01-28T16:06:57Z

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (16.1.0 → 16.1.6)

Sorry, we couldn't find anything useful about this release.

✳️ next (16.1.0 → 16.1.6) · Repo

Security Advisories 🚨

🚨 Next.js has Unbounded Memory Consumption via PPR Resume Endpoint

A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the Next-Resume: 1 header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion:

Unbounded request body buffering: The server buffers the entire POST request body into memory using Buffer.concat() without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory.

Unbounded decompression (zipbomb): The resume data cache is decompressed using inflateSync() without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion.

Both attack vectors result in a fatal V8 out-of-memory error (FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server.

To be affected, an application must run with experimental.ppr: true or cacheComponents: true configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable.

Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.

🚨 Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23864.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. This can result in denial of service in unpatched environments.

🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

A DoS vulnerability exists in self-hosted Next.js applications that have remotePatterns configured for the Image Optimizer. The image optimization endpoint (/_next/image) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that remotePatterns is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain.

Strongly consider upgrading to 15.5.10 and 16.1.5 to reduce risk and prevent availability issues in Next applications.

Release Notes

16.1.5

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
https://vercel.com/changelog/summary-of-cve-2026-23864

16.1.4

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Only filter next config if experimental flag is enabled (#88733)

Credits

Huge thanks to @mischnic for helping!

16.1.3

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Fix linked list bug in LRU deleteFromLru (#88652)

Fix relative same host redirects in node middleware (#88253)

Credits

Huge thanks to @acdlite and @ijjk for helping!

16.1.2

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Turbopack: Update to swc_core v50.2.3 (#87841) (#88296)

Fixes a crash when processing mdx files with multibyte characters. (#87713)

Turbopack: mimalloc upgrade and enabling it on musl (#88503) (#87815) (#88426)

Fixes a significant performance issue on musl-based Linux distributions (e.g. Alpine in Docker) related to musl's allocator.

Other platforms have always used mimalloc, but we previously did not use mimalloc on musl because of compilation issues that have since been resolved.

Credits

Huge thanks to @mischnic for helping!

16.1.1

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Turbopack: Create junction points instead of symlinks on Windows (#87606)

Credits

Huge thanks to @sokra and @ztanner for helping!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 26 commits:

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu cancel merge
Cancels automatic merging of this PR

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

coderabbitai · 2026-01-28T16:09:11Z

Walkthrough

The changes update dependency versions in two package.json files under playgrounds. Both playgounds/nextjs/package.json and playgrounds/v3/package.json bump next from ^16.1.0 to ^16.1.6 and eslint-config-next from ^16.1.0 to ^16.1.6. There are no functional changes or modifications to exported/public entities. Each file shows 2 lines added and 2 lines removed corresponding to the version updates.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating Next.js and related dependencies from version 16.1.0 to 16.1.6, accurately reflecting the security patch nature of the changes.
Description check	✅ Passed	The description is directly related to the changeset, providing detailed context about the security vulnerabilities being fixed, release notes, and specific CVEs affecting Next.js versions being updated.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

depfu · 2026-01-28T16:21:05Z

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.

depfu · 2026-01-29T14:40:01Z

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.

This PR bumps a bunch of dependencies. This also moves a few dependencies that we use in multiple packages to the pnpm catalog. Closes: #19603, #19604, #19576, #19575, #19573, #19565, #19547, #19546, #19545, #19609, #19581, #19620, #19619 - #19603 - #19604 - #19576 - #19575 - #19573 - #19565 - #19547 - #19546 - #19545 - #19609 - #19581 - #19620 - #19620 - #19619 ## Test Plan All tests in CI should still pass. [ci-all]

depfu · 2026-02-04T11:39:06Z

Closing because this update has already been applied

depfu bot requested a review from a team as a code owner January 28, 2026 16:06

depfu bot added the depfu label Jan 28, 2026

RobinMalfait mentioned this pull request Jan 28, 2026

Bump dependencies #19608

Merged

This was referenced Jan 28, 2026

Update all of nextjs 16.1.0 → 16.1.4 (patch) #19604

Closed

🚨 [security] Update all of nextjs 16.1.0 → 16.1.5 (patch) #19603

Closed

Update all of nextjs to version 16.1.6

6f9f438

depfu bot force-pushed the depfu/update/pnpm/group/nextjs-16.1.6 branch from fb7258b to 6f9f438 Compare January 29, 2026 14:20

depfu bot closed this Feb 4, 2026

depfu bot deleted the depfu/update/pnpm/group/nextjs-16.1.6 branch February 4, 2026 11:39

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

🚨 [security] Update all of nextjs 16.1.0 → 16.1.6 (patch)#19609

🚨 [security] Update all of nextjs 16.1.0 → 16.1.6 (patch)#19609
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/group/nextjs-16.1.6

depfu bot commented Jan 28, 2026 •

edited

Loading

Uh oh!

coderabbitai bot commented Jan 28, 2026 •

edited

Loading

Uh oh!

depfu bot commented Jan 28, 2026

Uh oh!

depfu bot commented Jan 29, 2026

Uh oh!

depfu bot commented Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

depfu bot commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed?

✳️ eslint-config-next (16.1.0 → 16.1.6)

✳️ next (16.1.0 → 16.1.6) · Repo

Core Changes

Credits

Core Changes

Credits

Core Changes

Credits

Core Changes

Credits

Uh oh!

coderabbitai bot commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Uh oh!

depfu bot commented Jan 28, 2026

Uh oh!

depfu bot commented Jan 29, 2026

Uh oh!

depfu bot commented Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

depfu bot commented Jan 28, 2026 •

edited

Loading

coderabbitai bot commented Jan 28, 2026 •

edited

Loading